Analyzing writing using pressure sensing touchscreens

ABSTRACT

The present invention provides a computer implemented method, a system, and a computer program product for verifying a writing of a user. In an exemplary embodiment, the present invention includes in response to receiving a writing on a pressure sensing touchpad logically coupled a computer system, recording a position and a pressure of one or more points of the writing via a pressure sensing touchscreen, executing a set of logical operations normalizing the writing, comparing the normalized writing to one or more stored writing parameters, executing a set of logical operations determining the normalized writing is within a tolerance of writing parameter deviation limits, thereby verifying the writing, and in response to determining the writing is within the tolerance of writing parameter deviation limits, storing, by the computer system, a value indicating that the writing is valid.

BACKGROUND

The present disclosure relates to pressure sensing touchscreens, andmore specifically, to analyzing writing using pressure sensingtouchscreens.

SUMMARY

The present invention provides a computer implemented method, a system,and a computer program product for verifying a writing of a user. In anexemplary embodiment, the present invention includes in response toreceiving a writing on a pressure sensing touchpad logically coupled toa computer system, recording a position and a pressure of one or morepoints of the writing via the pressure sensing touchscreen. The computersystem may execute a set of logical operations normalizing the writing.Also, the computer system may compare the normalized writing to one ormore stored writing parameters. In an embodiment, the computer systemexecutes a set of logical operations determining the normalized writingis within a tolerance of writing parameter deviation limits, therebyverifying the writing. In response to determining the writing is withinthe tolerance of writing parameter deviation limits, the computer systemmay store a value indicating that the writing is valid. In a furtherembodiment, the computer system executes a set of logical operationsdetermining the normalized writing is not within the tolerance ofwriting parameter deviation limits. In response to determining thewriting is not within the tolerance of writing parameter deviationlimits, the computer system may store a value indicating that thewriting is not valid.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a flowchart in accordance with an exemplary embodiment ofthe present invention.

FIG. 2 depicts a flowchart in accordance with an exemplary embodiment ofthe present invention.

FIG. 3 depicts an exemplary writing in accordance with an exemplaryembodiment of the present invention.

FIG. 4 depicts a section of an exemplary writing in accordance with anembodiment of the present invention.

FIG. 5 depicts a graph in accordance with an embodiment of the presentinvention.

FIG. 6 depicts two versions of a writing in accordance with an exemplaryembodiment of the present invention.

FIG. 7 depicts a computer system in accordance with an exemplaryembodiment of the present invention.

FIG. 8 depicts a cloud computing environment according to variousembodiments of the present invention.

FIG. 9 depicts abstraction model layers according to various embodimentsof the present invention.

DETAILED DESCRIPTION

The present invention provides a computer implemented method, a system,and a computer program product for verifying a writing of a user. In anexemplary embodiment, the present invention includes in response toreceiving a writing on a pressure sensing touchpad logically coupled toa computer system, recording a position and a pressure of one or morepoints of the writing via the pressure sensing touchscreen. The computersystem may execute a set of logical operations normalizing the writing.Also, the computer system may compare the normalized writing to one ormore stored writing parameters. In an embodiment, the computer systemexecutes a set of logical operations determining the normalized writingis within a tolerance of writing parameter deviation limits, therebyverifying the writing. In response to determining the writing is withinthe tolerance of writing parameter deviation limits, the computer systemmay store a value indicating that the writing is valid. In a furtherembodiment, the computer system executes a set of logical operationsdetermining the normalized writing is not within the tolerance ofwriting parameter deviation limits. In response to determining thewriting is not within the tolerance of writing parameter deviationlimits, the computer system may store a value indicating that thewriting is not valid.

Problems with Signature Verification

Many merchants and businesses use credit card scanners that require acustomer to sign an electronic device, but no real signatureverification is done on a backend server to process a transaction.Currently, the onus of signature verification is on cashiers performingthe transactions. Merchants are instructed to verify a signature bymatching it to a signature on the back of a card, but this is notcommonly done because it slows down transaction time. Even if merchantsdo check signatures, they give no real surety because cashiers are notgraphology experts. Newer smart card readers do provide more security byperforming sophisticated public key cryptography operations, but stilldo not perform any kind of verification on a signature. Nearly half ofall credit card fraud is done through internet based transactions, andthe most common personal verification of a user for an internettransaction is entering a CVV/CVC code from the back of a card. Penmovement recording devices do exist today, but they rely on the penitself to determine data for verification, not the screen itself. Theloss due to fraud continues to grow every year. A better method of fraudprotection is needed.

With dynamic signature verification, it is not the shape or look of thesignature that is meaningful. Instead, the change in speed, pressure,location, and/or timing that occur during the act of signing aremeaningful. Only the original signer can sufficiently recreate thechanges in speed, pressure, location, and/or timing. Point of salemanufacturers and suppliers are motivated to invest in security controlsto maintain their relationships with retailers.

Pressure Sensing Touchscreens

Pressure sensing touchscreens detect changes in pressure applied to thesurface of a screen. For example, pressure sensing touchscreens coulddetermine a range of readings corresponding to touches of a range ofdifferent pressures. In one example, the range could be limited to onlytwo types of touch, a hard touch, and a soft touch. In an alternativeexample, the range could produce distinct readings corresponding to thedegree of sensitivity and range of the pressure sensing touchscreen.

Using Writing Verification to Complete a Transaction

Referring to FIG. 1, in an exemplary embodiment, the present inventionis configured to perform a method 100. Method 100 may include anoperation 110 in response to receiving a writing on a pressure sensingtouchpad logically coupled a computer system, recording a position and apressure of one or more points of the writing via a pressure sensingtouchscreen. Method 100 may also include an operation 120 of executing,by the computer system, a set of logical operations normalizing thewriting. In an embodiment, method 100 includes an operation 130 ofcomparing, by the computer system, the normalized writing to one or morestored writing parameters. Method 100 may include an operation 140 ofexecuting, by the computer system, a set of logical operationsdetermining the normalized writing is within a tolerance of writingparameter deviation limits, thereby verifying the writing. Method 100may also include an operation 150 of in response to determining thewriting is within the tolerance of writing parameter deviation limits,storing, by the computer system, a value indicating that the writing isvalid.

In an embodiment, the present invention allows for a type of signatureverification to provide surety against fraudulent users. For example,the present invention could be used at a transaction terminal with apressure sensing touchscreen, or for online purchases by verifying asignature on the pressure sensing touchscreen of a personal device. Inan embodiment, the present invention uses pressure sensing touchscreensto electronically verify a signature through pressure and location data.The present invention could be used with existing pressure sensingtouchscreen technology and future pressure sensing touchscreens. Sincecustomers are accustomed to signing for a transaction already, thepresent invention could provide enhanced security without a drasticchange for users.

Referring to FIG. 2, in an exemplary embodiment, the present inventionis configured to perform a method 200. A computer system performsoperation 205 of scanning a credit card and operation 210 of activatingan account. A processor communicatively coupled to the computer systemperforms operation 215 in response to the activating the account,setting a value for allowed signature attempts. An electronic componentperforms operation 220 of prompting a user for a signature. Operation230 of recording one or more points of a signature on a pressure sensingtouchscreen logically coupled to the processor is performed by thepressure sensing touchscreen. Operation 235 of recording a pressure onthe pressure sensing touchscreen at the one or more points is performedby the pressure sensing touchscreen.

The computer system performs operation 240 of checking if the user hascompleted the signature. In response to the signature not beingcompleted yet, the computer system returns to operation 230. Thecomputer system performs operation 245 in response to the signaturebeing completed, normalizing the signature. The computer system performsoperation 250 of comparing the normalized signature to a stored writingparameter. The computer system performs operation 260 of checking if thenormalized signature is within a tolerance. The computer system performsoperation 270 in response to the normalized signature being within thetolerance, processing a transaction. The computer system performsoperation 275 in response to the normalized signature not being withinthe tolerance, subtracting a value of 1 (one) from the value of allowedsignature attempts. The computer system performs operation 280 ofchecking if the value for allowed signature attempts is equal to zero.The computer system performs operation 290 in response to the value forallowed signature attempts equaling 0 (zero), rejecting the transaction,and in response to the value for allowed signature attempts not equaling0 (zero), returning to operation 220.

Credentials

In an embodiment, the credentials are associated with an account. In anembodiment, the credentials include credit card information, and theaccount is the credit account associated with the card. In anembodiment, the credentials are credit card information, and the accountis the credit account associated with the card. For example, thecredentials could be linked to a bank account. In another example, thecredentials are linked to one of a savings account, a brokerage account,or a financial account.

In an embodiment, credentials are associated with an account. In oneembodiment, the credentials are credit card numbers, and the account isa financial account. For example, the financial account could be asavings account, a checking account, a retirement account, a brokerageaccount, a bank account, a credit card account, a debit card account, agift card account, a college savings account, or a points account. In anembodiment, account credentials are stored on a smart card used for atransaction.

Writing

In an embodiment, the writing is any electronic writing that needs to beverified. In an embodiment, the writing is a signature of the user, andthe stored writing parameter is a compilation of previous signatures ofthe user. In an embodiment, the writing includes a signature. Forexample, the writing could be a signature written on a pressure sensingtouchscreen of a mobile device. In an embodiment, the writing is asignature written on a pressure sensing touchscreen of a checkoutterminal. In one embodiment, the transaction is terminated if thesignature does not match a recorded signature parameter. In oneembodiment, signature data from a fraudulent transaction is recorded andanalyzed in an attempt to identify the fraudulent user. For example,signature data from a fraudulent transaction could be recorded andanalyzed to be used as evidence against a fraudulent user. In anembodiment, the writing is a signature of a user, and the one or morestored writing parameters corresponds to previous signatures of theuser.

Writing Instrument

In an embodiment, the writing is done by at least one of a humanappendage, a stylus, a rod, a pen, a computer mouse, a pointer, anelectronic writing instrument, or a writing instrument. For example, anyobject that could be used to apply pressure to a pressure sensingtouchscreen device could be used to make the signature.

In an embodiment, the pressure sensing touchscreen is a tablet computerused as a financial transaction terminal. For example, if a customerwere called upon to sign an electronic receipt, the customer could usehis/her finger or any object to sign on the pressure sensingtouchscreen.

In one embodiment, a stored writing parameter is stored for each type ofwriting implement. In a further embodiment, a stored writing parameteris stored for each category of writing implement.

Computer System

In an embodiment, the computer system is a credit card terminal used forcompleting credit card transactions. For example, if a pressure sensingtouchscreen were installed on the credit card terminal, a credit card isswiped to activate an account of a user.

In an embodiment, the pressure sensing touchscreen is a pressure sensingtouchscreen of a mobile device. In an embodiment, the computer system isa tablet computer, and the pressure sensing touchscreen iscommunicatively coupled to the computer system/tablet. In a furtherembodiment, the tablet computer is used as a checkout terminal. In analternative embodiment, the computer system is a mobile phone, and thepressure sensing touchscreen is the screen communicatively coupled tothe mobile phone. In one example, the user could link a mobile phone toa register and complete a transaction using the mobile phone. Forexample, the user links the mobile phone to a checkout terminal andsigns on the mobile phone instead of signing out on the checkoutterminal. In a further embodiment, the checkout terminal is any registeror credit card device. In an alternative embodiment, the user could linkthe mobile phone to a website and complete a transaction using themobile phone. For example, the user could link the mobile phone to anonline shopping site and sign a purchase agreement or receipt on thepressure sensing touchscreen communicatively coupled to the mobilephone.

In an embodiment, the pressure sensing touchscreen is a pressure sensingtouchscreen communicatively coupled to a mobile device. For example, thepressure sensing touch screen could be the screen communicativelycoupled to one of a cellular phone, a tablet computer, a laptopcomputer, a music player, a smartwatch, a smart phone, a gaming device,or an automobile.

Recording a Position and a Pressure

In one embodiment, the stored writing parameter is pressure/positiondata for one or more previous signatures. Referring to FIG. 3 and FIG.4, in an exemplary embodiment, a user has pressure/position data storedfor one or more previous writings with account information, andpressure/position data is recorded for a new signature to be compared tothe stored pressure/position data.

FIG. 3 details a section 310 of a signature 300. A user signature 300 isanalyzed for pressure/position data to compare to the storedpressure/position data. As depicted in FIG. 4, the pressure/positiondata is recorded at the starting position 320 and at one or morepositions 410, 420 of the signature. In one embodiment, the processordetermines a difference between a pen and a finger based on thedifferences in the reading, recorded on the pressure sensingtouchscreen, between the two when signing. For example, a finger has alarger footprint than a stylus. In an embodiment, the number of the oneor more points recorded is based on an importance of the signatureverification. In an embodiment, the sampling rate of the writing couldbe tailored to requirements of the application. The sampling rate isrelated to the number of pressure/position readings taken for a givenwriting. For example, a smaller sampling rate for pressure and locationdata could be used on transactions with a low value, thereby creating asmaller dataset to save space and time. In another example, a highersampling rate for pressure and position data could be used ontransactions with a high value to ensure a more detailed comparison ismade. The finger could exert pressure over a larger area than thestylus, but the stylus could exert more pressure per unit area. In anembodiment, the tolerance is based on an importance of the verifying thewriting. In an embodiment, the number of the one or more points forwhich the position and the pressures are recorded is based on animportance of the verifying the writing.

Referring to FIG. 5, in an exemplary embodiment, the pressure/positiondata is charted. The position data is converted into a line length 580for the signature and charted against pressure 590 to make graph 500.The data is charted for starting point 510 and one or more points alongthe signature length. Lines 520, 540, 550, 560, and 570 show where awriting instrument stopped exerting any pressure on the pressure sensingtouchscreen at various points along the signature. In an example, thestarting point 420 of the Eli portion 515 of the signature 400corresponds to point 510, and the end point 425 of the Eli portion 515of the signature corresponds to point 512. The data used to plot graph500 is be used to compare the signature to data stored for previoussignatures.

Normalizing the Writing

In an embodiment, the stored writing parameter is a compilation ofprevious signatures of the user. For example, if the user signs thepressure sensing touchscreen. The signature is normalized and comparedindividually to a series of previously stored signatures from the user.For example, a first letter of the normalized signature could match afirst letter of one previously stored signature, and a second letter ofthe normalized signature could match the second letter of a secondpreviously stored signature. In an alternative embodiment, the signatureis compared to data derived from a series of previously storedsignatures. In one embodiment, a pressure reading at a certain positionof the normalized signature is compared to a range of values compiledfrom readings at that position for previous signatures. For example, fora signature containing a “C”, a pressure reading of the normalizedsignature at a point of the “C” could be compared to a range of valuesfor the pressure readings at the same point of the same letter “C” onprevious signatures. If the new reading is within the range of theprevious readings, then the point is verified as matching. If thereading does not fall within the range of the previous readings, thenthe point is not verified. In one example the range could be defined asno more than ten percent below the lowest previous reading and no morethan ten percent above the highest reading.

In an embodiment, the normalization is done to account for screens ofdifferent sizes. In one embodiment, the normalization is to account fordifferent orientations of the signature. In one embodiment, thenormalization is done to account for different devices. In oneembodiment, the normalization is done to account for the differencesbetween writing implements. In one embodiment, the signatures arenormalized to account for pressure sensing touchscreens of differentpressure sensitivities.

In an embodiment, any of operations 120, 130, 140, and 150 is performedon one or more cloud computing nodes. In an embodiment, stored writingparameters are stored on more or more cloud computing nodes.

Referring to FIG. 6, in an embodiment, a current transaction signature650 is normalized for size to be compared to a stored signature 600.Referring to Equation 1, an X factor is determined by dividing a length(ls) 620 of stored signature 600 by a length (lt) 670 of currenttransaction signature 650.

$\begin{matrix}{x_{factor} = \frac{l_{s}}{l_{t}}} & ( {{Equation}\mspace{14mu} 1} )\end{matrix}$

Referring to Equation 2, in an embodiment, a Y factor is determined bydividing a height (hs) 610 of stored signature 600 by a height (ht) 660of current transaction signature 650.

$\begin{matrix}{y_{factor} = \frac{h_{s}}{h_{t}}} & ( {{Equation}\mspace{14mu} 2} )\end{matrix}$

Referring to Equations 3 and 4, in an embodiment, a normalizedcoordinate for the current transaction signature is calculated by takingany given X coordinate multiplied by the calculated X factor and anygiven Y coordinate multiplied by the calculated Y factor.

(x _(n norm))=(x _(n) *x _(factor))  (Equation 3)

(y _(n norm))=(y _(n) *y _(factor))  (Equation 4)

In one embodiment, normalization to account for different screensensitivities is accomplished by relating the relative pressure of eachpoint to the maximum and minimum pressures recorded in the currenttransaction signature 650. Referring to Equation 5, in one embodiment, anormalization number (f_(bit)) for a given touchpad is calculated bysubtracting the minimum pressure (p_(min)) recorded at any bit from themaximum pressure (p_(max)) recorded at any bit and dividing that numberby the register size factor (2^(register size)).

$\begin{matrix}{f_{bit} = {\frac{p_{\max} - p_{\min}}{2^{{register}\mspace{14mu} {size}}} = \frac{Force}{Bit}}} & ( {{Equation}\mspace{14mu} 5} )\end{matrix}$

Referring to Equation 6, the bit value is then calculated by subtractingthe minimum pressure (p_(min)) from the pressure at the specific xylocation (p_(n)) and dividing that number by the result from Equation 5.

$\begin{matrix}{{{bit}\mspace{14mu} {value}} = \frac{p_{n} - p_{\min}}{f_{bit}}} & ( {{Equation}\mspace{14mu} 6} )\end{matrix}$

In an alternative embodiment, the normalizing is done by amicroprocessor on a smartcard linked to an account, the comparing isdone by the microprocessor on the smartcard, and the signature valuesare stored on the smartcard.

Comparing

In a further embodiment, the stored writing parameter is a compilationof previous signatures of the user. In one embodiment, the storedwriting parameter is a set of writings given specifically for use inverification. In an alternative embodiment, the stored writing iscompiled from writings given for other purposes besides solely forverification purposes. For example, the stored writing parameter couldbe some of the previous signatures used to complete previoustransactions. A backend server could record signature pressure data fromthe first few transactions with the credit card to create a signature onfile. In an alternative example, a user could be required to recordhis/her signature upon issuance of the credit card.

In an embodiment, the stored writing parameter is a compilation ofprevious signatures of the user. In an embodiment, separate signatureparameters are recorded and stored relating to different writingmethods. In an embodiment, separate signature parameters are recordedand stored relating to different writing implements.

In an embodiment, credentials are associated with an account. In anembodiment, the credentials include previous signature data. In afurther embodiment, the signature data is constantly monitored andupdated as a user continues using an account. For example, a signaturecould change over time and thus the writing parameters need to change.In a further example, as the pressure sensing screen technologycontinues to improve the signature data needs to be updated to match newtechnology.

In an embodiment, signature pressure data is saved in a database serveron a smartcard. In an embodiment, signature pressure data is saved on amobile device. In an embodiment, the stored writing parameter is storedon a server.

Tolerance of Writing Parameter Deviation Limits

In an embodiment, the tolerance is based on the importance of thesignature verification. In an embodiment, the tolerance is set by anoperator of the computer system depending on the importance of gainingaccess to the account. For example, accessing calendar information couldbe set to a relaxed tolerance as it is deemed not important, butaccessing personal information such as a social security number could beset to a strict tolerance. In a further example, for an access deemedimportant, where the stored writing parameter pressure is 10 Pa (Pascal)at a point in a writing, the tolerance would be set for the computersystem to accept 8-12 Pa, or a 20% variation, at the point. Whereas, foran access deemed not important, where the stored writing parameterpressure is 10 Pa at a point in a writing, the tolerance would be set toaccept 5-15 Pa, or a 50% variation, at the point. In one embodiment, thetolerance is linked to the value of a transaction. The higher thetransaction value, the stricter the tolerance. Smaller purchases couldhave relaxed tolerances so as not to impede the transactions by falserejections of a writing. Larger transactions, of higher risk, could havestrict tolerances to prevent fraudulent purchases. In an example,accessing credit card information for a small transaction is deemed notimportant and therefore set to a relaxed tolerance. However accessingcredit card information for a large transaction is deemed important andtherefore set to a strict tolerance. In a further example, signaturesfor Health Insurance Portability and Accountability Act (HIPAA), signinga title or deed to a property, or signing a contract could be deemedimportant. In a further example, signatures for terms for using awebsite could be deemed not important.

In one embodiment, a comparison of the pressure of the normalizedsignature is made to the pressure of the signature on file to determinethe validity of the signature. The degree of correlation between thenormalized signature and the signature on file is then be used todetermine if a transaction should be verified.

Verifying/Rejecting

In an embodiment, the computer implemented method, the system, and thecomputer program product further include, in response to the activatingand determining, by the computer system, a set of logical operationscomparing the recorded writing to the one or more stored writingparameters based on a tolerance, where one outcome includes averification of the writing, where one outcome includes rejecting of thewriting and the transaction.

In an embodiment, in response to the comparing, the computer systemdetermines the normalized writing is not within the tolerance of writingparameter deviation limits, thereby rejecting the writing and returningto the prompting. In an embodiment, the transaction is canceled after afailed number of attempts.

In an embodiment, if the writing is verified, computer system proceedswith a transaction. If the writing is rejected the computer systemsubtracts a value of 1 (one) from a value of signature attempts. In oneembodiment, the value for signature attempts starts at a set number. Inan alternative embodiment, the value for signature attempts start at anumber based on the importance of a transaction. In a furtherembodiment, when the writing is rejected, the computer system subtractsa value of 1 (one) from the value for signature attempts. If the valueis equal to zero, the computer system rejects the transaction. If thevalue is greater than zero, the computer system repeats one or moresteps of the process.

In one embodiment, other factors are used in conjunction with pressuredata to verify a signature. Other factors could include strokedirection, stroke speed, order of crossed t's and dotted i's, and timeto complete signature.

In one embodiment, a backup system is used for situations where theuser's signature did not match after exhausting all signature attempts.For example, a backup could be necessary if there was an injury to ahand normally used to sign or the signature device malfunctions. In oneembodiment, the backup system is one of a pin code, a password,presenting an identification card, presenting a photo identificationcard, responding to a text on an authorized phone, responding to a phonecall on an authorized phone, or responding to an email on an authorizedaccount.

In an exemplary embodiment, the computer system is a standalone computersystem, such as computer system 700 shown in FIG. 7, a network ofdistributed computers, where at least some of the computers are computersystems such as computer system 700 shown in FIG. 7, or a cloudcomputing node server, such as computer system 700 shown in FIG. 7. Inan embodiment, the computer system is a computer system 700 as shown inFIG. 7, that executes a managing signature verification script orcomputer software application that carries out the operations of atleast method 100. In an embodiment, the computer system is a computersystem/server 712 as shown in FIG. 7, that executes a managing signatureverification script or computer software application that carries outthe operations of at least method 100. In an embodiment, the computersystem is a computer system 700 as shown in FIG. 7, that executes amanaging signature verification script or computer software applicationthat carries out at least method 100. In an embodiment, the computersystem is a computer system/sever 712 as shown in FIG. 7, that executesa managing signature verification script or computer softwareapplication that carries out at least method 100.

Computer System

In an exemplary embodiment, the computer system is a computer system 700as shown in FIG. 7. Computer system 700 is only one example of acomputer system and is not intended to suggest any limitation as to thescope of use or functionality of embodiments of the present invention.Regardless, computer system 700 is capable of being implemented toperform and/or performing any of the functionality/operations of thepresent invention.

Computer system 700 includes a computer system/server 712, which isoperational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 712 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices.

Computer system/server 712 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, and/or data structuresthat perform particular tasks or implement particular abstract datatypes. Computer system/server 712 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 7, computer system/server 712 in computer system 700 isshown in the form of a general-purpose computing device. The componentsof computer system/server 712 may include, but are not limited to, oneor more processors or processing units 716, a system memory 728, and abus 718 that couples various system components including system memory728 to processor 716.

Bus 718 represents one or more of any of several types of busstructures, including a memory bus or memory controller, a peripheralbus, an accelerated graphics port, and a processor or local bus usingany of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronics Standards Association (VESA) local bus, andPeripheral Component Interconnects (PCI) bus.

Computer system/server 712 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 712, and includes both volatile andnon-volatile media, removable and non-removable media.

System memory 728 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 730 and/or cachememory 732. Computer system/server 712 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 734 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 718 by one or more datamedia interfaces. As will be further depicted and described below,memory 728 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions/operations of embodiments of the invention.

Program/utility 740, having a set (at least one) of program modules 742,may be stored in memory 728 by way of example, and not limitation.Exemplary program modules 742 may include an operating system, one ormore application programs, other program modules, and program data. Eachof the operating system, one or more application programs, other programmodules, and program data or some combination thereof, may include animplementation of a networking environment. Program modules 742generally carry out the functions and/or methodologies of embodiments ofthe present invention.

Computer system/server 712 may also communicate with one or moreexternal devices 714 such as a keyboard, a pointing device, a display724, one or more devices that enable a user to interact with computersystem/server 712, and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 712 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 722. Still yet, computer system/server 712 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 720. As depicted, network adapter 720communicates with the other components of computer system/server 712 viabus 718. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 712. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems.

Cloud Computing

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 8, illustrative cloud computing environment 850 isdepicted. As shown, cloud computing environment 850 includes one or morecloud computing nodes 810 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 854A, desktop computer 854B, laptop computer 854C,and/or automobile computer system 854N may communicate. Nodes 810 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 850 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 854A-Nshown in FIG. 8 are intended to be illustrative only and that computingnodes 10 and cloud computing environment 850 can communicate with anytype of computerized device over any type of network and/or networkaddressable connection (e.g., using a web browser).

Referring now to FIG. 9, a set of functional abstraction layers providedby cloud computing environment 850 (FIG. 8) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 9 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 90 includes hardware and softwarecomponents. Examples of hardware components include: mainframes; RISC(Reduced Instruction Set Computer) architecture based servers; storagedevices; networks and networking components. In some embodiments,software components include network application server software.

Virtualization layer 92 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 94 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 96 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and mobile desktop.

Computer Program Product

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present disclosurehave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A computer implemented method comprising: inresponse to receiving a writing on a pressure sensing touchscreenlogically coupled to a computer system, recording a position and apressure of one or more points of the writing via the pressure sensingtouchscreen wherein the number of the one or more points for which theposition and the pressure are recorded is based on an importance of theverifying the writing; comparing, by the computer system, the writing toone or more stored writing parameters; executing, by the computersystem, a set of logical operations determining the writing is within atolerance of writing parameter deviation limits, thereby verifying thewriting; and in response to determining the writing is within thetolerance of writing parameter deviation limits, storing, by thecomputer system, a value indicating that the writing is valid.
 2. Themethod of claim 1 further comprising: executing, by the computer system,a set of logical operations determining the writing is not within thetolerance of writing parameter deviation limits; and in response todetermining the writing is not within the tolerance of writing parameterdeviation limits, storing, by the computer system, a value indicatingthat the writing is not valid.
 3. The method of claim 1, wherein thewriting is a signature of a user and wherein the one or more storedwriting parameters corresponds to previous signatures of the user. 4.The method of claim 1, wherein the tolerance is based on an importanceof the verifying the writing.
 5. The method of claim 1, wherein thewriting is done by at least one of a human appendage, a stylus, a rod, apen, a computer mouse, a pointer, an electronic writing instrument, anda writing instrument.
 6. The method of claim 1, wherein the pressuresensing touchscreen is a pressure sensing touchscreen of a mobiledevice.
 7. A system comprising: a memory; and a processor incommunication with the memory, the processor configured to perform amethod comprising, in response to receiving a writing on a pressuresensing touchscreen logically coupled to a computer system, recording aposition and a pressure of one or more points of the writing via thepressure sensing touchscreen wherein the number of the one or morepoints for which the position and the pressure are recorded is based onan importance of the verifying the writing; executing, by the computersystem, a set of logical operations the writing; comparing, by thecomputer system, the writing to one or more stored writing parameters;executing, by the computer system, a set of logical operationsdetermining the writing is within a tolerance of writing parameterdeviation limits, thereby verifying the writing; and in response todetermining the writing is within the tolerance of writing parameterdeviation limits, storing, by the computer system, a value indicatingthat the writing is valid.
 8. The system of claim 7 further comprising:executing, by the computer system, a set of logical operationsdetermining the writing is not within the tolerance of writing parameterdeviation limits; and in response to determining the writing is notwithin the tolerance of writing parameter deviation limits, storing, bythe computer system, a value indicating that the writing is not valid.9. The system of claim 7, wherein the writing is a signature of a userand wherein the one or more stored writing parameters corresponds toprevious signatures of the user.
 10. The system of claim 7, wherein thetolerance is based on an importance of the verifying the writing. 11.The system of claim 7, wherein the writing is done by at least one of ahuman appendage, a stylus, a rod, a pen, a computer mouse, a pointer, anelectronic writing instrument, and a writing instrument.
 12. The systemof claim 7, wherein the pressure sensing touchscreen is a pressuresensing touchscreen of a mobile device.
 13. A computer program productcomprising a computer readable storage medium having programinstructions embodied therewith, the program instructions executable bya processor to cause the processor to perform a method comprising: inresponse to receiving a writing on a pressure sensing touchscreenlogically coupled to a computer system, recording a position and apressure of one or more points of the writing via the pressure sensingtouchscreen wherein the number of the one or more points for which theposition and the pressure are recorded is based on an importance of theverifying the writing; comparing, by the computer system, the writing toone or more stored writing parameters; executing, by the computersystem, a set of logical operations determining the writing is within atolerance of writing parameter deviation limits, thereby verifying thewriting; and in response to determining the writing is within thetolerance of writing parameter deviation limits, storing, by thecomputer system, a value indicating that the writing is valid.
 14. Thecomputer program product of claim 13 further comprising: executing, bythe computer system, a set of logical operations determining the writingis not within the tolerance of writing parameter deviation limits; andin response to determining the writing is not within the tolerance ofwriting parameter deviation limits, storing, by the computer system, avalue indicating that the writing is not valid.
 15. The computer programproduct of claim 13, wherein the writing is a signature of a user andwherein the one or more stored writing parameters corresponds toprevious signatures of the user.
 16. The computer program product ofclaim 13, wherein the tolerance is based on an importance of theverifying the writing.
 17. The computer program product of claim 13,wherein the pressure sensing touchscreen is a pressure sensingtouchscreen of a mobile device.